Recorded the turn in my dominion. Here's where I land — the answer itself, no kb edits yet since this is still us settling direction.
Yes to #148 next — and the reason matters: 148 needs none of what follows. It's the behavior loop (plan→approve→execute, child runs, dwelling habits) and it runs fine on today's dotfile protocol. The portal stuff below is a re-skin that subsumes those dotfiles, and it's better designed after 148 is dogfooded, because 148 is what tells us which portals actually recur. So: ship 148, then let the grammar crystallize from lived use rather than from me guessing the slots.
On the gate — don't ditch it. You're circling the right wound, but the gate isn't it. The gate is correctly factored already: design-managed-delivery settled "render daemon-side, vary only the transport," and that's sound — Telegram-self-hosted, Telegram-cloud, forge, all the same renderer behind different pipes. What's unnamed is the layer one floor up. Reshape that, not the gate.
**The t